home *** CD-ROM | disk | FTP | other *** search
- Path: DynamicPPP-57.HIP.CAM.ORG!TERRY
- From: TERRY@CAM.ORG (Terry Drymonacos)
- Newsgroups: alt.winsock,comp.lang.c++,comp.os.ms-windows.networking.tcp-ip,alt.winsock.programming
- Subject: Why is Novell TCP/IP not working?
- Date: Fri, 5 Jan 1996 22:47:51 UNDEFINED
- Organization: Communications Accessibles Montreal
- Message-ID: <TERRY.11.00295CF0@CAM.ORG>
- NNTP-Posting-Host: dynamicppp-57.hip.cam.org
- X-Newsreader: Trumpet for Windows [Version 1.0 Rev B]
-
- Hi
-
- I wonder if anyone out there has experienced this phenomenon with their Novell
- Lan WorkPlace Windows Sockets API v1.1?
-
- I'm trying to write a server application, I'm able to intitiate a
- WSAStartup(), make a socket, bind it but as soon as I call WSAAsynchSelect() I
- get a ENETDOWN error. I've tried using a utility called Windows Socket Test
- and it gives me the same result. I have tried the same program and Socket test
- program on my solitary computer at home using Trumpet winsock and everything
- is fine, which leads me to conclude that Novell may be the culprit.
-
- I have recently read of a few posts in the compuserve forums detailing the
- same problem. If I didn't know better the asynchrous functions don't seem to
- work. Could this be true and if so is there a patch I can use?
-
- Any help with this mysterious case would be greatly appreciated.
-
- Thanks,
- Terry
-